I like this addition. Thank you! 🙂

About the syntax highlighting: I would stick with nunjucks.

An additional thought on this: I wonder a little whether it would make sense to recommend the getDom method, even if it is perhaps a little more complicated.

Two reasons:

• Learning effect: What you learn in the process can be applied to other projects. It is rather unlikely that you will encounter Nunjucks anywhere else in another modern project. However, it certainly doesn't hurt to familiarize yourself with the concept of a templating system.
• Future: Nunjucks seems to me to be a project that Mozilla has abandoned without further development from a community. Will it still be compatible in five years, or will we perhaps even have to remove it from the core at some point?

I researched active alternatives, but everything I found would entail breaking changes. Currently, there isn't really a problem, but I suspect that one will arise in the long term. The last Nunjucks release was in 2023 – maybe I'm painting too early a picture of the devil on the wall here 😈

@KristjanESPERANTO Fixed that casing!

And good question, we're definitely in a bit of a pickle on how we'd ever remove it.

I feel like unless it gets officially deprecated, we shouldn't add anything telling folks to not use it.

Personally, I always use the templates, as I find imperatively building out a frontend to be pretty tedious. Honestly, when I realized I could use templates is probably when I got the most into building modules! So I've always appreciated that it was there.

Maybe in the long run it should be up to modules to BYOT (bring your own templating), but that could increase the size of modules.

It does seem there is still some current interest in the project, and they are right now actively bumping dependencies and working on things, but who knows the future there.

But as long as it is there, I'll be championing declarative frontends!